[e2e tests] Wait for secondary IPs before running ping test #6041
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antoninbas
added
area/test/e2e
For VLAN Secondary Network e2e tests, we need to wait for secondary IPs to be available. Interface creation can take up to a few seconds after the Pod is in the Running state, as it happens asynchronously. Otherwise we can get the following error: secondary_network_test.go:194: Error when pinging between interfaces: interface eth1 not found on vlan-pod2. err: <nil> Fixes antrea-io#6023 Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
antoninbas
force-pushed
the
wait-for-secondary-ips-to-run-ping-test
branch
from
41d0113
to
98d8255
Compare
Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
jianjuns
approved these changes
Mar 1, 2024
|
/test-all |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For VLAN Secondary Network e2e tests, we need to wait for secondary IPs to be available. Interface creation can take up to a few seconds after the Pod is in the Running state, as it happens asynchronously. Otherwise we can get the following error:
Fixes #6023